Systems and methods for gated media access based on collections of unique digital articles

ABSTRACT

Systems and methods to providing gated media access based on collections and/or combinations of unique digital articles in an online gaming platform are disclosed. Exemplary implementations may execute instances of a game; manage user accounts associated with the users, including a first and a second user account associated with a first and a second user; receive, from the first user, a first access request to access particular media content, wherein the access requires ownership of a first and a second (type of) unique digital article (as recorded on an immutable ledger); permit the first access request (and other similar requests) as long as the first user is the registered owner of the first and second (type of) unique digital articles.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods to gated media access based on collections and/or combinations of unique digital articles.

BACKGROUND

Online gaming platforms are known. Distributed ledgers are known techniques to produce a secure record or registry of ownership of articles, transactions, and other information. Many types of digital articles are known.

SUMMARY

One aspect of the present disclosure relates to a system configured to provide gated media access, based on collections of unique digital articles. The system may include one or more processors configured by machine-readable instructions. The system may be configured to execute instances of a game. The system may be configured to manage user accounts associated with the users, including a first user account associated with a first user, wherein a first account inventory includes a first and a second unique digital article. The system may be configured to receive, from the first user, a first access request to access particular media content, wherein the access requires ownership of the first and second unique digital articles (or those types of articles, as recorded on an immutable ledger). The system may be configured to permit the first access request (and other similar requests) as long as the first user is the registered owner of the first and second unique digital articles (or those types of articles).

Another aspect of the present disclosure related to a method of providing gated media access based on collections of unique digital articles in an online gaming platform. The method may include executing instances of a game. The method may include managing user accounts associated with the users, including a first user account associated with a first user, wherein a first account inventory includes a first and a second unique digital article. The method may include receiving, from the first user, a first access request to access particular media content, wherein the access requires ownership of the first and second unique digital articles (or those types of articles, as recorded on an immutable ledger). The method may include permitting the first access request (and other similar requests) as long as the first user is the registered owner of the first and second unique digital articles(or those types of articles).

As used herein, any association (or relation, or reflection, or indication, or correspondency, or correlation) involving servers, processors, client computing platforms, users, user accounts, inventories, articles, articles, requests, manners of usage, exchanges, challenges, offers, transactions, in-game actions, rights, benefits, ownership, immutable ledgers, responses, denials, contracts, metrics, metric values, scores, gains, trigger events, incentives, proposals, sets of instructions, operations, determinations, distributions, transfers, presentations, interfaces, notifications, and/or another entity or object that interacts with any part of the system and/or plays a part in the operation of the system, may be a one-to-one association, a one-to-many association, a many-to-one association, and/or a many-to-many association or “N”-to-“M” association (note that “N” and “M” may be different numbers greater than 1).

As used herein, the term “obtain” (and derivatives thereof) may include active and/or passive retrieval, determination, derivation, transfer, upload, download, submission, and/or exchange of information, and/or any combination thereof. As used herein, the term “effectuate” (and derivatives thereof) may include active and/or passive causation of any effect, both local and remote. As used herein, the term “determine” (and derivatives thereof) may include measure, calculate, compute, estimate, approximate, generate, and/or otherwise derive, and/or any combination thereof.

These and other features, and characteristics of the present technology, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of ‘a’, ‘an’, and ‘the’ include plural referents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to provide gated media access, based on collections of unique digital articles, in accordance with one or more implementations.

FIG. 2 illustrates a method for providing gated media access, based on collections of unique digital articles, in accordance with one or more implementations.

FIGS. 3-4 illustrate example implementations of user interfaces, as may be used by a system configured to provide gated media access, based on collections of unique digital articles, in accordance with one or more implementations.

FIGS. 5A-5B illustrates exemplary blockchains, as may be used by a system configured to provide gated media access, based on collections of unique digital articles, in accordance with one or more implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to provide gated media access 105, based on collections of unique digital articles, in accordance with one or more implementations. As used herein, the term “unique digital article” may refer to digital articles that are uniquely identified and/or uniquely identifiable, e.g., by an identifier or by identifying information. For example, in some implementations, an identifier or identifying information may include or be based on a combination of different types of information, including but not limited to information regarding the type of a digital article, a serial number or other numerical identifier of the digital article, and/or other types of information. As used herein, ownership of unique digital articles may be tracked, recorded, and/or otherwise registered on one or more immutable ledgers. As such, a unique digital article may be a ledger-tracked unique digital article.

Individual unique digital articles may be associated and/or correlated with another entity (which may be referred to as a “correlated entity”) by virtue of technology provided and/or supported by the one or more immutable ledgers on which the ownership of the individual unique digital articles is tracked (including but not limited to smart contracts and/or other executable code on the one or more immutable ledgers). Accordingly, ownership of a unique digital article may correlate to the provision of one or more rights with respect to the correlated entity (e.g., control and/or other rights). Transactions involving a unique digital article recorded on an immutable ledger may correlate to certain transactions (or modifications) of the correlated entity, and/or vice versa.

In some implementations, correlated entities may be (or include) virtual items configured to be used within online-gaming platform 105 (such as, for example, a user-controllable in-game virtual character that is usable within an instance of a game within online gaming platform 105). Other types and/or combinations of correlated entities are envisioned within the scope of this disclosure, including but not limited to physical and/or virtual objects, items, rights, memberships, permissions, etc. The use of the singular “entity” or “correlated entity” is not intended to be limiting, as multiple different objects, items, rights, memberships, permissions, etc. may be correlated to a single unique digital article. By way of non-limiting example, a correlated entity may be an art work, a ticket to an event, a subscription to certain media content, a bundle of rights related to captured audio and/or video information, rights to distribution gains, and so forth. As used herein, the term “non-fungible token” or “NFT” may be used to refer to a combination of a particular unique digital article and a particular correlated entity that is correlated to the particular unique digital article.

System 100 may include one or more online gaming platforms 105, immutable ledger server(s) 111, administration server(s) 115, media server(s) 119, client computing platform(s) 104, user interface(s) 125, server(s) 102, external resource(s) 138, and/or other components. Users 123 (also referred to as players) may include one or more of a first user, a second user, a third user, a fourth user, an administrative user, and/or other users. Users 123 may include players who play and/or otherwise interact on online gaming platform 105. As used in descriptions herein, any use of the term “user” may refer to user(s) 123. Electronic storage 130 a, electronic storage 130 b, and electronic storage 130 c may be similar to electronic storage 130 as described elsewhere in this disclosure, though included in administration servers 115, immutable ledger servers 111, and media servers 119, respectively, as depicted in FIG. 1.

Instances of games may be executed within one or more online gaming platforms 105. As used herein, online gaming platform 105 may refer to either an individual game (e.g., an interactive online game), a type of gaming console and its ecosystem, and/or both. Online gaming platform 105 may be configured to host (and/or execute instances of) the one or more (online) games. Online gaming platform 105 may be operated, hosted, and/or owned by one or more stakeholders of online gaming platform 105. For example, a platform operator (and/or another stakeholder) may sell in-game digital items (e.g., characters, weapons, resources, etc.) to users 123 of online gaming platform 105.

Referring to the game and to online gaming platform 105, in some implementations, individual players may own and/or control individual unique digital articles, correlated entities, and/or other virtual items, and exchange these with (or to) other individual players. As used herein, exchanges refer to individual players winning, losing, auctioning, selling, purchasing, trading, bartering, wagering, staking, and/or otherwise exchanging virtual items (directly, without a store or store interface under control of online gaming platform 105) to other individual players or with other individual players (including exchanging virtual items through player-to-player challenges). Due to an exchange, ownership rights of a digital article may transition from an original owner to a new owner (even if there may, in some implementations, be one or more intermediary and/or temporary owners during the process of performing the exchange). In some implementations, unique digital articles may be associated and/or correlated with other rights than ownership rights, such as, by way of non-limiting example, distribution rights.

In some implementations, distribution rights of (unique) digital articles may reflect rights held by the individual ones of the users to receive certain distributions of benefits upon exchanges involving the particular digital articles. That is, the individual users may own/hold rights to particular digital articles that guarantee them benefits upon (future) exchanges involving those digital articles regardless of whether the individual users own/hold the ownership rights for those digital articles. In some implementations, the distribution gains may result from a particular action or activity (such as, e.g., a sale of a particular digital article), e.g., within the online gaming platform 105, of a particular digital article. As used herein, a distribution gain resulting from a particular action or activity may include one or more of a portion of the proceeds of the particular action or activity, a fee related to the particular action or activity, a minimum payment triggered by the occurrence of the particular action or activity (or a set of particular actions or activities), and/or another arrangement for payment and/or compensation, including but not limited to combinations of fixed fees, minimum fees, percentages of sales, percentages of profits, and/or other arrangements. The term “portion” does not imply or require a percentage or ratio, but rather is intended to signify that beneficiaries (i.e., the users that hold the distribution rights) may receive something of value and/or use. The distribution gains may include one or more virtual currencies such as virtual tokens, virtual stars, virtual points, virtual real-world currencies (e.g., US Dollars), and/or other gains that are based on the particular digital articles.

In some implementations, unique digital articles, correlated entities, and/or other virtual items may include and/or be virtual items that are not fungible and may be usable within an online gaming platform 105. In some implementations, these may represent (three-dimensional) in-game user-controllable characters that can interact with other (in-game) virtual items within online gaming platform 105. In some implementations, virtual items may include one or more of weapons, toys, characters, abilities, skills, tools, pets, clothing, vehicles, game levels, missions, assignments, chapters, tasks, mini-games, restricted areas within a virtual space, restricted modes of gameplay, access rights within an online game, and/or other virtual items. In some implementations, virtual items may refer to any item or object within online gaming platform 105 for which a user may use, own, sell, trade, destroy, and/or otherwise effectuate a change of ownership or control (including exchanging through challenges).

As used herein, a digital article is fungible if it is functionally and/or physically indistinguishable from another digital article. For example, a payment token such as a Bitcoin is fungible. A digital article may be non-fungible if it is unique, or one-of-a-kind. For example, a specific individual CryptoKitty™ may be non-fungible. A digital article may be semi-fungible if there is a set of a limited number of similar but distinguishable digital articles. For example, a limited-edition Blanko™ or another in-game character may be semi-fungible. For example, one of a limited number of 2-dimensional or 3-dimensional in-game virtual items may be semi-fungible. For example, a digital ticket to a show, concert, exhibition, and/or other event may be semi-fungible. For example, a piece of art or jewelry (e.g., as a virtual item or as representing a physical item) may be semi-fungible. As used herein, semi-fungible digital articles are considered as unique, “not fungible”, or non-fungible digital articles. In some implementations, digital articles may be usable within one or more games.

Immutable ledger server(s) 111 (e.g., immutable ledger server 111 a, immutable ledger server 111 b, and so forth) may be used to implement one or more immutable ledgers, including but not limited to blockchain 117 a, blockchain 117 b (partially visible in FIG. 1), and so forth. In some implementations, one or more immutable ledgers may be decentralized ledgers. In some implementations, blockchain 117 a and blockchain 117 b may be maintained by distributed computing platforms (not shown in FIG. 1). In some implementations, a distributed computing platform may be implemented by a set of client computing platforms and/or servers (including, for example, one or more immutable ledger servers 111). The distributed computing platform may support a virtual machine (not shown in FIG. 1). The distributed computing platform and/or the virtual machine may form a runtime environment for smart contracts and/or other executable code. A distributed computing platform may include electronic storage configured to store part or all of blockchain 117 a. For example, the smart contracts may be stored on blockchain 117 a, blockchain 117 b, and/or another immutable ledger. In some implementations, the distributed computing platform may be the EOSIO platform. In some implementations, the distributed computing platform may be similar to or based on the EOSIO platform. In some implementations, the distributed computing platform may be Ethereum. In some implementations, the distributed computing platform may be similar to or based on Ethereum. In some implementations, the virtual machine may be a decentralized virtual machine.

In some implementations, at least one of the immutable ledgers implemented by immutable ledger servers 111 is a private permissioned immutable ledger. The private permissioned blockchain may be configured to record information. The recorded information may include information pertaining to unique digital articles that are associated and/or correlated with in-game user-controllable characters that are configured to be used in an instance of a game. The recorded information may include ownership of the unique digital articles. Implementing the in-game actions in the instance of the game may include, for at least some of the in-game actions implemented in the instance of the game, effectuating modifications to the recorded information pertaining to the unique digital article. For example, ownership rights and/or other rights may be modified. In some implementations, a unique digital article may be removed from one immutable ledger and added or recorded on another immutable ledger. In some implementations, at least one of the immutable ledgers implemented by immutable ledger servers 111 is a public immutable ledger. The public immutable ledger may be configured to be part of either EOSIO mainnet, Ethereum mainnet, Ethereum 1.5, Ethereum 2.0, a derivative of Ethereum 2.0 that is configured to perform transactions of Ether (ETH) between accounts, or a derivative of EOSIO that is configured to perform transactions of EOS between different accounts.

Elements of blockchain 117 a or another immutable ledger may be grouped together in units that are referred to as blocks. For example, an individual block may include one or more digital articles (or digital assets) and one or more transactions. For example, an individual block may be linked to one or more other individual blocks. Individual blocks may be linked or chained together to form a structure of blocks and/or a hierarchy of blocks, such as, e.g., a chain of blocks. An individual block may include one or more digital articles, one or more transactions, and/or other information.

In some implementations, one or more immutable ledgers implemented by immutable ledger servers 111 may be publicly accessible. In some implementations, one or more immutable ledgers implemented by immutable ledger servers 111 may be private and/or permissioned. In some implementations, one or more immutable ledgers implemented by immutable ledger servers 111 may be append-only. In some implementations, existing blocks of one or more immutable ledgers implemented by immutable ledger servers 111 can substantially not be altered or deleted, unless multiple copies are altered. This is unlikely to happen provided that the multiple copies stored on different computing platforms, e.g., in different geographical locations. Immutable ledgers may be replicated on multiple computing platforms, preferably in multiple different geographical locations. Additionally, individual blocks may be linked together in a manner that prevents tampering, such as, e.g., using a hash chain and/or digital signatures. In particular, hash values may be generated using fixed-output-length one-way hashing functions that take variable-length input, and may be effectively impossible (or, at least, computationally infeasible) to reverse. As such, a hashing function may provide one-way encryption. By way of non-limiting example, the hashing function may be SHA-256, BLAKE2, SHAKE256, and/or another hashing function. Contents of individual blocks, transactions, and/or articles may be digitally signed in a manner that proves integrity and/or prevents tampering, e.g., by providing authentication, as well as repudiation.

As depicted in FIG. 1, immutable ledger server 111 a may include one or more of electronic storage 130 b, processor(s) 132 b, machine-readable instructions 106 b, (node of) blockchain 117 a, and/or other components. Machine-readable instructions 106 b may include one or more instruction components. The instruction components may include computer program components. The instruction components may include one or more of a transaction component 134, a receipt component 136, and/or other instruction components. In some implementations, an individual immutable ledger server may be dedicated to a particular node of an immutable ledger. Typically, different nodes are included in (or implemented by, or hosted by) different servers or different computer systems to increase the safety and security of transactions on a blockchain. The consensus protocol used for a particular blockchain will be harder to falsify or circumvent when the different nodes are in different geographical locations, on different types of computing platforms, and/or otherwise distributed and diverse. As depicted in FIG. 1, blockchain 117 a may include a unique digital article 15 (by way of non-limiting example, unique digital article 15 may be correlated with a user-controllable in-game character, as depicted, and ownership of unique digital article 15 may have been recorded on blockchain 117 a, as depicted). Immutable ledger server 111 b may include similar components as immutable ledger server 111 a, including but not limited to blockchain 117 b and/or other components.

Media server(s) 119 may include one or more of electronic storage 130 c, processor(s) 132 c, machine-readable instructions 106 c, and/or other components. Machine-readable instructions 106 c may include one or more instruction components. The instruction components may include computer program components. The instruction components may include one or more of a request component 139, an ownership component 141, an access component 143, and/or other instruction components. In some implementations, an individual media server (e.g., a content distribution platform) may be dedicated to a particular type of media content. In some implementations, one or more media servers 119 may be configured to provide a media-specific service to users 123. By way of non-limiting example, media-specific services may include YouTube™, Discord™, Instagram™, Facebook™, Patreon™, Twitch™, Substack™, SoundCloud™, and/or other services. By way of non-limiting example, media content provided by one or more media servers 119 may include one or more of previously-recorded video messages, live-streaming video channels, text chat channels, blog posts, previously-recorded audio content, live-streaming audio channels, and/or other media content. By way of non-limiting example, a particular media server 119 may provide streaming music to users, or podcasts, or other media content.

Server(s) 102 may be configured to communicate with one or more client computing platforms 104 according to a client/server architecture and/or other architectures. Client computing platform(s) 104 may be configured to communicate with other client computing platforms via server(s) 102 and/or according to a peer-to-peer architecture and/or other architectures. Users may access system 100 via client computing platform(s) 104. In some implementations, system 100 and/or immutable ledger server(s) 111 may be configured to communicate with one or more of online gaming platform(s) 105, users 123, and/or other entities and/or components, e.g., through one or more networks 13.

Server(s) 102 may include electronic storage 130, processor(s) 132, machine-readable instructions 106, and/or other components. Server(s) 102 may be configured by machine-readable instructions 106. Machine-readable instructions 106 may include one or more instruction components. The instruction components may include computer program components. The instruction components may include one or more of a game component 108, an interaction component 110, an account component 112, a recording component 114, an availability component 116, a performance component 118, a ledger-analysis component 120, a notification component 122, a distribution component 124, an adjustment component 126, a ledger component 128, a reward component 131, a presentation component 133, transaction component 134, receipt component 136, an input component 135, a communication component 137, request component 139, ownership component 141, access component 143, and/or other instruction components. Processor(s) 132 a, processor(s) 132 b, and processor(s) 132 c may be similar to processor(s) 132 as described elsewhere in this disclosure, though included in administration servers 115, immutable ledger servers 111, and media servers 119, respectively, as depicted in FIG. 1. Machine-readable instructions 106 a, machine-readable instructions 106 b, and machine-readable instructions 106 c may be similar to machine-readable instructions 106 as described elsewhere in this disclosure, though included in administration servers 115, immutable ledger servers 111, and media servers 119, respectively, as depicted in FIG. 1.

Game component 108 is configured to execute, via online gaming platform 105, one or more instances of one or more games. An instance of a game may facilitate presentation of the game to users 123. For example, the instance of the game may be an online game executed with online gaming platform 105. Game component 108 may be configured to implement in-game actions in the instance of the game, e.g., in response to (action) requests for the in-game actions by the users. In some implementations, game component 108 may be arranged, organized, and/or otherwise included in online gaming platform 105. As used herein, the term “game” may refer to one or more games within online gaming platform 105. In some implementations, the game may be provided via a virtual space, and may include a plurality of resource types and/or maps.

The presentation of the game may be based on the views of the game that are determined during execution of the game, e.g., as based on instructions and/or other input from users. In some implementations, the view may be communicated (e.g., by streaming, via object/position data, and/or other information) from online gaming platform 105, immutable ledger server(s) 111, and/or other sources to client computing platforms 104 for presentation to users 123. The view determined and transmitted to a given client computing platform 104 may correspond to a location in the virtual space (e.g., the location from which the view is taken, the location the view depicts, and/or other locations), a zoom ratio, a dimensionality of objects, a point-of-view, and/or view parameters. In some implementations, one or more view parameters may be selectable by a user.

The instance of the game may include a simulated space that is accessible by users 123 by clients (e.g., client computing platforms 104) that present the views of the virtual space to a user. The simulated space may have a topography, express ongoing real-time interaction by one or more users 123, and/or include one or more objects positioned within the topography that are capable of locomotion and/or movement within the topography. In some implementations, the topography may be a 2-dimensional topography. In some implementations, the topography may be a 3-dimensional topography. The topography may include dimensions of the simulated space, and/or surface features of a surface or objects that are native to the simulated space. In some implementations, the topography may include a surface (e.g., a ground surface) that runs through at least a substantial section of the simulated space. In some implementations, the topography may describe a volume with one or more bodies positioned therein. The instance executed by the computer components may be synchronous, asynchronous, and/or semi-synchronous.

Within the instance of the game, users 123 may control characters, objects, simulated physical phenomena, and/or other elements within the virtual space to interact with the virtual space and/or each other. The characters may include avatars. As used herein, the term “character” or “user character” may refer to an object or group of objects present in the virtual space, that correspond(s) to an individual user. A particular user character may be controlled by the particular user with which it is associated. Such user characters may be referred to as user-controlled characters. User-controlled element(s) may move through and interact with the virtual space (e.g., non-user characters in the virtual space, other objects in the virtual space, etc.). In some implementations, user-controlled characters may be capable of locomotion within the topography of the simulated space that is included in the instance of the game. In some implementations, the topography may include one or more restricted areas that are only accessible under certain conditions. In some implementations, user-controlled elements controlled by and/or associated with a given user may be created and/or customized by the given user. Individual users 123 or user accounts may own or control an “inventory” of virtual goods and currency (e.g., resources of the plurality of resource types) that the individual user can use (e.g., by manipulation of a user character and/or other user-controlled elements) and/or other items, to perform in-game actions within the virtual space. By way of non-limiting illustration, users 123 may include the first user and the second user that interact with online gaming platform 105. The first user and the second user may control digital articles (e.g., characters) in a game hosted by online gaming platform 105. In some implementations, account inventories may be managed (at least in part) using blockchain 117 a. For example, ownership rights (and/or other types of rights) of individual virtual items included in an individual account inventory may be recorded on blockchain 117 a. In some implementations, at least some individual virtual items (also referred to as correlated entities) may correlate to individual unique digital articles (that may be tracked by immutable ledger servers 111). In some implementations, individual account inventories may correspond to individual smart contracts stored on blockchain 117 a.

Interaction component 110 may be configured to enable, facilitate, and/or implement in-game actions by users 123 in instances of games. In some implementations, interaction component 110 may be configured to operate in response to instructions and/or (action) requests by users 123. Interaction component 110 may be configured to receive requests from users 123, e.g., action requests to perform in-game actions in the instance of the game. By way of non-limiting example, in-game actions may include one or more of performing a move, a dance, a movement, or another action within the game, accessing a level or area within the game, using a particular item, weapon, or another resource within the game, participating in a particular game mode (e.g., a Battle Royale mode), join a particular mission or team, engage in a particular type of exchange and/or challenge between players, and/or other in-game actions. For example, one or more users may interact within online gaming platform 105 to build, create, gather, find, combine, and/or otherwise generate content (i.e., user-generated content). In some implementations, a user request may request access to a particular type or section of a store and/or marketplace within online gaming platform 105.

In some implementations, operations may be accomplished by interaction component 110 through user interfaces 125. In particular, operations pertaining to a particular user may be accomplished or controlled or initiated through a particular user interface 125 of a particular client computing platform 104, where the particular client computing platform 104 is associated with the particular user. In other words, the particular user may interact with an instance of a game through interaction component 110 and/or the particular user interface 125. In some implementations, operations by interaction component 110 may be limited, restricted, and/or otherwise controlled by other components of system 100, including but not limited to availability component 116. In some implementations, interaction component 110 may require acceptance from particular users. For example, an acceptance may accept a particular offer to partake in an activity or agreement. In some implementations, interaction component 110 may be configured to receive indications of acceptances and/or other agreements from users.

In some implementations, interaction component 110 may be configured to facilitate interaction of users 123 with system 100. In some implementations, interaction component 110 may be configured to facilitate interaction by users 123 through user interfaces 125. For example, a particular user may be associated with a particular client computing platform 104, which may include a particular user interface 125. In other words, an individual user interface may be user-specific and/or specific to a particular client computing platform. In some implementations, interaction component 110 may facilitate entry and/or selection through (presentation of) one or more user interfaces 125 (such as, by way of non-limiting example, any of the interfaces described in this disclosure).

Account component 112 is configured to manage user accounts. User accounts may be associated with users 123. User accounts may include and/or be associated with account inventories of virtual items. For example, the user accounts may include a first user account associated with a first user, a second user account associated with a second user, and so forth. For example, the first user account may include a first account inventory of one or more virtual items, and so forth. Individual users may control one or more virtual items in their individual account inventories. In some implementations, the first account inventory includes one or more unique digital articles (e.g., a first unique digital article, a second unique digital article, etc.). The first unique digital article may be correlated with a first in-game user-controllable character configured to be used (e.g., played with) in the instance of the game. The second unique digital article may be correlated with a second in-game user-controllable character configured to be used (e.g., played with) in the instance of the game, and so forth.

In some implementations, account component 112 may be configured to manage user accounts that are specific to a particular online gaming platform 105 and/or a specific game provided by the particular online gaming platform 105. For example, account component 112 may be configured to manage user accounts that are specific to one or more media servers 119 (and/or to a media-specific service provided through media servers 119). In some implementations, an individual user may be associated with a first user account on a particular online gaming platform 105 and a second user account on a particular media server 119. In other words, the same user may have different user accounts for online gaming platform(s) 105 and media server(s) 119.

Recording component 114 is configured to record articles on immutable ledgers. In some implementations, recording component 114 may record and/or modify ownership of articles. In some implementations, recording component 114 may be configured to receive (recordation) requests to perform a recordation (e.g., of a unique digital article on an immutable ledger). For example, recording component 114 may receive, on behalf of a first user, a recordation request to record and/or modify ownership of a first unique digital article on a first immutable ledger (such as, e.g., blockchain 117 a). In some implementations, recording component 114 may receive such requests from online gaming platform 105 and/or other components of system 100. For example, a particular request to record (ownership of) a particular unique digital article may correspond to the issuance and/or creation of that particular unique digital article. When a unique digital article or other digital article is issued and/or created, recording component 114 may record its ownership on a particular immutable ledger. In some implementations, a particular request to modify ownership of a particular unique digital article may correspond to an exchange of that particular unique digital article (e.g., between two users).

Availability component 116 may be configured to determine whether particular action requests are available to particular users. In some implementations, availability may require and/or other be based on ownership of specific unique digital articles (or types of specific unique digital articles, and/or combinations of both). For example, the specific availability of a specific action request (i.e., the in-game action requested in the specific action request) may require ownership of a particular collection and/or combination of digital articles. For example, the particular combination may include unique digital articles. In some implementations, the particular combination may include one or more of multiple unique digital articles of the same type, or issued at the same time, or issued by a particular set of smart contracts, and/or released during the same drop. In some implementations, the particular combination may include one or more of unique digital articles awarded for participating in a particular online event, or a particular real-world event. In some implementations, the particular combination may include one or more unique digital articles that have received (and/or will receive) particular distribution gains by virtue of owning particular distribution rights. In some implementations, the particular combination may include one or more unique digital articles that have been obtained through a particular type of player-to-player challenge within an instance of a game. Different collections and/or combinations of multiple unique digital articles are envisioned within the scope of this disclosure. Determinations by availability component 116 may be used to control operations by other components of system 100, including but not limited to interaction component 110.

In some implementations, availability component 116 may be configured to determine whether particular users are eligible to receive one or more participation rewards or attendance awards for either a particular unique digital article participating in an online event or attending an online event (e.g., during a particular time-limited duration, or between a begin time and an end time of the online event). Alternatively, and/or simultaneously, availability component 116 may be configured to determine whether particular users are eligible to receive one or more participation rewards or attendance awards for participating in a real-world event or attending a real-world event (e.g., during a particular time-limited duration). In some implementations, availability component 116 may be configured to determine whether particular users are eligible to receive distribution gains by virtue of owning distribution rights for one or more particular unique digital articles.

Performance component 118 may be configured to permit and/or perform requested in-game actions, e.g., to use particular unique digital articles. In some implementations, permission to use a particular unique digital article in accordance with a particular action request may be granted based on one or more determinations by availability component 116. For example, permission may be granted for certain requested in-game actions, but not for others. For example, requested in-game actions may be performed if requested by a first user, but not a second user. In some implementations, performance component 118 may permit and/or perform some types of requests, but not other types of requests. In some implementations, permission and/or performance may be prevented for certain types of requests, unless the pertinent (required) combination of unique digital articles is currently recorded on a particular immutable ledger as being owned by a particular user or account.

In some implementations, permission and/or performance by performance component 118 may require not only a particular type of request, but additionally may require the pertinent unique digital article (or other digital article that is not fungible) currently be recorded on a particular immutable ledger (or type of immutable ledger). For example, a requirement for permission or performance may include recordation on a private permissioned immutable ledger. In some implementations, actions by performance component 118 may be performed responsive to particular actions or results from other components of system 100, including but not limited to availability component 116 and/or ledger-analysis component 120.

Ledger-analysis component 120 may be configured to determine whether one or more unique digital articles are recorded (on a particular immutable ledger) as being owned by a particular user and/or account. For example, ledger-analysis component 120 may determine whether a first unique digital article is currently recorded on a private permissioned immutable ledger. In some implementations, ledger-analysis component 120 may be configured to analyze recordations and other transactions on one or more immutable ledgers, e.g., by retrieving recorded information from the one or more immutable ledgers and analyzing whether any of the recorded transactions pertain to a particular unique digital article, or a set of unique digital articles. In some implementations, determinations by ledger-analysis component 120 may be performed responsive to particular actions or results from other components of system 100, including but not limited to availability component 116. In some implementations, ledger-analysis component 120 may be configured to determine whether ownership of a particular unique digital article (or other digital article that is not fungible) has ever been recorded on a public immutable ledger. For example, actions by other components of system 100, including but not limited to distribution component 124, may be responsive to determinations by ledger-analysis component 120. In some implementations, determinations by ledger-analysis component 120 may occur in real-time or near-real-time as needed for a particular action request or access request. In some implementations, determinations by ledger-analysis component 120 may occur as needed when ownership of (unique) digital articles is modified, and results of such determinations are stored for later use by, e.g., online gaming platform 105, e.g., to be used when responding to a future action request or a future access request.

Notification component 122 may be configured to notify users. For example, notification component 122 may notify users in response to action requests. In some implementations, a user may be notified responsive to a requested in-game action (as requested through an action request) not being permitted or not being performed (e.g., as determined by performance component 118). In some implementations, actions by notification component 122 may be performed responsive to particular actions, results, determinations, or decisions from other components of system 100, including but not limited to availability component 116, performance component 118, and/or ledger-analysis component 120. For example, notification component 122 may respond to a particular action request (by a particular user, and pertaining to a particular unique digital article) with a particular response such that, responsive to a particular determination, the particular response notifies the particular user that the particular user is not permitted.

Distribution component 124 may be configured to distribute and/or otherwise provide one or more of information, access to in-game content, access to game-specific communication channels, certificates, rewards, awards, prizes, distribution gains, and/or virtual items to users 123. Distributions by distribution component 124 may be adjusted, e.g., by adjustment component 126. In some implementations, distributions may be responsive to determinations by reward component 131. In some implementations, distributions may be based on and/or responsive to actions by other components of system 100, including but not limited to ledger-analysis component 120. For example, online gaming platform 105 may determine a particular user is eligible to receive one or more rewards or awards. Distribution component 124 may distribute the one or more rewards or awards in accordance with the determined eligibility. For example, a reward may be a participation reward. For example, an award may be an attendance award. For example, a certificate may be a certificate of completion or accomplishment, which may be specific to actions within the instance of the game. For example, a prize may be for effort, time, and/or resources spent, specifically in the instance of the game. For example, particular unique digital articles may be associated with distribution rights, and the particular user who owns those distribution rights may receive distribution gains in accordance with those distribution rights. For example, distribution gains may result from a particular action or activity (such as, e.g., a sale of a particular digital article), e.g., within the online gaming platform 105, involving the particular digital article.

Adjustment component 126 may be configured to adjust and/or modify distributions, including (planned or expected) distributions by distribution component 124. In some implementations, adjustment component 126 may adjust and/or modify one or more certificates, rewards, awards, prizes, distribution gains, and/or virtual items that have been determined by reward component 131 (also referred to as the determined distribution or the eligible distribution). Upon such adjustment and/or modification, this determined distribution (or eligible distribution) may be referred to as the adjusted distribution. Distribution component 124 may distribute the adjusted distribution. In some implementations, adjustments and/or modifications by adjustment component 126 may increase the value of one or more elements of the eligible distribution (this may provide a positive incentive to users). Alternatively, and/or simultaneously, adjustments and/or modifications by adjustment component 126 may decrease the value of one or more elements of the eligible distribution (this may provide a negative incentive to users). In some implementations, actions by adjustment component 126 may be performed responsive to particular actions or results from other components of system 100, including but not limited to availability component 116 and/or ledger-analysis component 120.

Ledger component 128 may be configured to generate sets of instructions for immutable ledger servers 111 (e.g., immutable ledger server 111 a) and/or one or more immutable ledgers (e.g., blockchain 117 a). In some implementations, ledger component 128 may be configured to transfer the generated sets of instructions to immutable ledger servers 111 and/or one or more immutable ledgers. In some implementations, one or more of these instructions may instruct the formation of a smart contract and/or the recording of the smart contract on the one or more immutable ledgers (e.g., blockchain 117 a). In some implementations, one or more of these instructions may call and/or otherwise invoke a method or function of a smart contract on the one or more immutable ledgers (e.g., blockchain 117 a). In some implementations, these instructions may instruct immutable ledger servers 111 to record and/or modify unique digital articles, transactions, and/or rights on one or more immutable ledgers, or to analyze ownership as recorded on the one or more immutable ledgers. For example, ledger component 128 may transfer a particular set of instructions that, upon execution by blockchain 117 a, issue a new unique digital article to a particular user or particular account (i.e., record the ownership of the new unique digital article as being owned by the particular user or the particular account). For example, ledger component 128 may transfer a particular set of instructions that, upon execution by blockchain 117 a and blockchain 117 b, remove a particular unique digital article from blockchain 117 a and add the particular unique digital article to blockchain 117 b. For example, ledger component 128 may transfer a particular set of instructions that, upon execution by blockchain 117 a and blockchain 117 b, analyze whether a particular user owns one or more particular unique digital articles.

Reward component 131 may be configured to determine eligibility for unique digital articles, other digital articles, accounts, and/or users 123 to receive one or more of information, access to in-game content, access to game-specific communication channels, certificates, rewards, awards, prizes, distribution gains, and/or virtual items. In some implementations, these types of determinations may be based on and/or responsive to actions by other components of system 100, including but not limited to ledger-analysis component 120. In some implementations, online gaming platform 105 may determine a particular user is eligible to receive one or more rewards or awards. Distributions in accordance with the determined eligibility may be made by distribution component 124. In some implementations, (one or more elements of) such eligible distributions may be adjusted and/or modified by adjustment component 126 prior to being distributed.

Presentation component 133 may be configured to present interfaces (e.g., user interfaces 125) to users, e.g., through client computing platforms 104 associated with the respective users. In some implementations, presentation component 133 may be configured to effectuate presentations of interfaces to users. The presented interfaces may include challenge interfaces, as described in this disclosure. In some implementations, presentations by presentation component 133 may be performed jointly (or at least in some cooperative manner) with one or both of game component 108 and/or interaction component 110. Presentation component 133 may present offers (from other users) to particular users, as described elsewhere in this disclosure.

Receipt component 136 may be configured to receive (sets of) instructions to add, modify, analyze, and/or remove recorded rights in blockchain 117 a. For example, receipt component 136 may receive one or more sets of instructions from ledger component 128, online gaming platform 105, and/or other components of system 100. Receipt component 136 may provide received sets of instructions to record component 134 for execution. In some implementations, execution of individual ones of the instructions received may include invoking one or more function calls of an Application Programming Interface (API) 107. For example, API 107 may be configured to provide interactive communication between blockchain 117 a and other components of system 100. For example, in some implementations, API 107 may support methods or functions that are implemented as function calls to smart contracts stored on blockchain 117 a. For example, in some implementations, API 107 may support methods or functions that analyze whether a particular user owns one or more particular unique digital articles, one or more particular types of unique digital articles, and/or a particular collection of multiple unique digital articles. In some implementations, receipt component 136 may be arranged, organized, and/or otherwise included in immutable ledger server 111 and/or blockchain 117 a.

Transaction component 134 may be configured to record (ownership) rights pertaining to digital articles, e.g., on blockchain 117 a. In some implementations, transaction component 134 may record rights on electronic storage 130 b. In some implementations, transaction component 134 may record rights on blockchain 117 a. The rights may include ownership rights, distribution rights, and/or other rights. For example, particular recorded rights may reflect ownership of a particular digital article by a particular user or group of users. For example, a particular unique digital article may represent a three-dimensional in-game user-controllable item or character that can interact with other virtual items within online gaming platform 105. Recorded rights may be specific to a digital article (i.e., article-specific). For example, distribution rights for a particular digital article may designate rights to certain distributions of benefits upon a specifically defined in-game action (e.g., an exchange between users) involving the particular digital article.

In some implementations, transaction component 134 may be configured to record rights in blockchain 117 a. In some implementations, transaction component 134 may add, modify, analyze, and/or remove recorded rights. For example, in accordance with received instructions from receipt component 136, transaction component 134 may transfer ownership of a particular digital article from a first owner to a second owner (e.g., from an original owner to a new owner, or from a loser of a challenge to a winner of the challenge) such that the recorded rights on blockchain 117 a no longer reflect the ownership of the particular digital article by the first user. In some implementations, in accordance with received instructions, transaction component 134 may transfer ownership of a particular digital article temporarily, e.g., from a first owner to a temporary second owner such as a smart contract. In some case, a temporary owner may be a holding account that is merely used until ownership is transferred to either the original owner or a new owner. As used herein, the term “temporary” (and derivatives thereof) refers to a transfer or to ownership that is either known to be changed and/or modified within a predetermined period, or expected to be changed and/or modified within a predetermined period. Conversely, a non-temporary transfer from a first owner to a second owner (due to a particular exchange) can conceivably be changed and/or reverted (back from the second owner to the first owner) due to a separate and new exchange that is independent of the first particular exchange. In some implementations, in accordance with received instructions, transaction component 134 may transfer ownership of a particular digital article non-temporarily from a first owner to a second owner, e.g., when a particular exchange is not reversible or no longer reversible. In some implementations, transaction component 134 may be arranged, organized, and/or otherwise included in blockchain 117 a.

In some implementations, transaction component 134 may be configured to obtain article-specific rights (e.g., ownership rights, distribution rights, and/or other rights) for particular digital articles. In some implementations, transaction component 134 may be configured to access blockchain 117 a to obtain the article-specific rights (that are recorded on blockchain 117 a, e.g., in one or more smart contracts).

Input component 135 may be configured to receive user input from administrative users. For example, the user input may include entry and/or selection of particular information, unique digital articles, types of digital articles, virtual items, types of virtual items, and/or any entity or object that interacts with any part of system 100 and/or plays a part in the operation of system 100. For example, an administrative user may select a particular set of unique digital articles (e.g., all “Camo Blankos” that have been issued) as the input set of unique digital articles for other components of system 100, such as availability component 116. Additionally, in some implementations, the administrative user may select a particular adjustment to be enacted by adjustment component 126 (e.g., increase the value of one or more elements of the eligible distribution) for one or more types of determinations by reward component 131 (e.g., an eligible distribution of a reward of 100 virtual coins for leveling up a unique digital article in the selected set of unique digital articles). As another example, the administrative user may select a different set of unique digital articles (e.g., all “Boss Dino Blankos” that have been issued) as the input set of unique digital articles for other components of system 100. Additionally, the administrative user may select a particular adjustment to be enacted by adjustment component 126 (e.g., decrease the value of one or more elements of the eligible distribution) for one or more types of determinations by reward component 131 (e.g., an eligible distribution may be receiving the distribution gains based on particular in-game actions for unique digital articles in the selected set of unique digital articles).

Communication component 137 may be configured to facilitate communication and/or interaction between administration server 115 and the rest of system 100. For example, communication component 137 may communicate user input received by input component 135 to other components of system 100, particularly of online gaming platform 105.

Request component 139 may be configured to receive requests from users 123, or on behalf of users 123. The requests may include access requests, requests for information, and/or other requests. Access requests may request to access particular media content. By way of non-limiting example, particular media content may include one or more of a previously-recorded video message, a live-streaming video channel, a text chat channel, a blog post, previously-recorded audio content, a live-streaming audio channel, and/or other media content. In some implementations, an access request may be specific to a particular action or activity on a particular media channel. For example, a particular access request may request to post a message or talk on a particular Discord™ channel. In some implementations, the requested access may require ownership of one or more digital articles, one or more unique digital articles, and/or one or more types of unique digital articles, or any combination thereof. For example, an access request for a particular type of action on a Blanko-specific media channel may require ownership of a collection of unique digital articles including at least a first particular unique digital article and a second particular unique digital article (e.g., a “Camo Blanko” and a “Dazzle Blanko”).

Ownership component 141 may be configured to determine whether particular users are recorded (and/or otherwise registered) as owning particular digital articles, including but not limited to particular collections of unique digital articles. Ownership component 114 may be configured to make determinations responsive to requests received (e.g., by request component 139) from users. In some implementations, ownership component 141 may be configured to access one or more immutable ledger servers 111 and/or one or more immutable ledgers (e.g., blockchain 117 a) to make particular determinations. In some implementations, ownership component 141 may be configured to use ledger component 128, ledger-analysis component 120, and/or another component of system 100 to make particular determinations.

Access component 143 may be configured to permit or deny access to particular media content. In some implementations, access component 143 may be configured to permit or deny access to particular media content to one or more particular users. In some implementations, access component 143 may be configured to permit or deny access based on determinations by ownership component 141. For example, assume a particular type of action on a Blanko-specific media channel requires ownership of a collection of unique digital articles including at least a first particular unique digital article and a second particular unique digital article (e.g., a “Camo Blanko” and a “Dazzle Blanko”). Assume a first user, who owns a “Camo Blanko” but not a “Dazzle Blanko”, requests access to the Blanko-specific media channel. Responsive to a determination by ownership component 141, access component 143 may deny the requested access. Subsequently, the first user obtains a “Dazzle Blanko”, and again requests access to the Blanko-specific media channel. Responsive to another determination by ownership component 141, access component 143 may grant access as requested.

Referring to FIG. 1, user interfaces 125 may be configured to facilitate interaction between users 123 and system 100 and/or between users 123 and client computing platforms 104. For example, user interfaces 125 may provide an interface (e.g., a challenge interface) through which users 123 may provide information to and/or receive information from system 100. In some implementations, user interface 125 may include one or more of a display screen, touchscreen, monitor, a keyboard, buttons, switches, knobs, levers, mouse, microphones, sensors to capture voice commands, sensors to capture body movement, sensors to capture hand and/or finger gestures, and/or other user interface devices configured to receive and/or convey user input. In some implementations, one or more user interfaces 125 may be included in one or more client computing platforms 104. In some implementations, one or more user interfaces 125 may be included in system 100. In some implementations, user interface 125 may be a type of interface that facilitates the exchange of virtual items between users.

FIG. 3 illustrates an example implementation of a user interface 300 as may be used by system 100, in accordance with one or more implementations. User interface 300 may enable a particular user to view and/or use an account inventory and/or one or more unique digital articles controlled by the particular user. User interface 300 may include a section or field for account inventory 31, and/or other graphical user interface elements. As depicted, account inventory 31 may include a list of different virtual items and/or articles currently controlled by the particular user, including virtual items 1-2-3-4-5. Account inventory 31 further depicts item information regarding these virtual items, as indicated by item information 1-2-3-4-5, which correspond to virtual items 1-2-3-4-5, respectively. Account inventory 31 as depicted may further include graphical user interface elements such as, by way of non-limiting example, an action button 32 (which initiates an action request). Upon engagement by the particular user, action request button 32 may request “virtual item 1” to be used for a particular request by the particular user (e.g., through a text field or a dropdown menu, as indicated by a triangle in a box). For example, the particular user may request to post information about unique digital article 15 on a particular media channel (not depicted), and unique digital article 15 may be associated with a user-controllable in-game character that is also depicted in user interface 300. This type of access request may be permitted and subsequently performed if and only if the particular requesting user currently owns a combination of a first particular unique digital article (of a first type of unique digital articles, such as, e.g., a “Camo Blanko”) and a second particular unique digital article (of a second type of unique digital articles, such as, e.g., a “Dazzle Blanko”).

FIG. 4 illustrates an example implementation of a user interface 300 a as may be used by system 100, in accordance with one or more implementations. User interface 300 a is similar to user interface 300 in FIG. 3. User interface 300 a in FIG. 4 may enable a particular user to view and/or use an account inventory and/or one or more unique digital articles controlled by the particular user. User interface 300 a may include a section or field for account inventory 31, and/or other graphical user interface elements. As depicted, account inventory 31 may include a list of different virtual items and/or articles currently controlled by the particular user, including virtual items 1-2-3-4-5. Account inventory 31 further depicts item information regarding these virtual items, as indicated by item information 1-2-3-4-5, which correspond to virtual items 1-2-3-4-5, respectively. Account inventory 31 as depicted may further include graphical user interface elements such as, by way of non-limiting example, an action button 32. Upon engagement by the particular user, action request button 32 may request “virtual item 1” to be used for a particular request (e.g., through a text field or a dropdown menu, as indicated by a triangle in a box. User interface 300 a as depicted may further include graphical user interface elements such as, by way of non-limiting example, a notification element 33 a. Upon engagement by the particular user of action request button 32, and responsive to this particular request being denied, notification element 33 a is displayed to the particular user, labeled “You can't post this information unless you own both a Camo Blanko and a Dazzle Blanko.” In this case, the requested access to a particular media channel is not permitted and the response to this particular access request includes displaying notification element 33 a.

FIG. 5A illustrate exemplary blockchain 117 c as may be used by system 100, in accordance with one or more implementations. FIG. 5A illustrates a blockchain 117 c that includes a block 0, a block 1, and a block 2. As time progresses, more blocks may be added to blockchain 117 c. The blocks within blockchain 117 c are ordered. In block 0, one article (indicated by a capital “A”) is generated and/or assigned to user “i” (U_(i)). A second digital article, a smart contract 15 a is assigned to user “a” (U_(a)), and a third digital article, a smart contract 16 a, is assigned to user “a” (U_(a)), which may be an administrative user. For example, smart contract 15 a and smart contract 16 a may be or include templates for issuing particular types of unique digital articles. Smart contract 15 a and smart contract 16 a may have been posted to blockchain 117 c by a component similar to record component 134.

For example, the articles in block 0 may be individual ownership rights recorded for particular digital articles within an online gaming platform. Block 1 is connected to block 0 (as indicated by a link 50 a), for example by including an address of block 1 in block 0, or vice versa. Likewise, block 1 is connected to block 2, as indicated by a link 50 b. In block 1, a transaction to smart contract 15 a (indicated by “Ax”) is recorded. Transaction Ax to smart contract 15 a may issue a unique digital article to user “p”, the unique digital article being defined by metadata 52 (here, correlated to a user-controllable character named “Camo Blanko”, having identifier “#001”, as depicted by a linked image of unique digital article 15, as well as including various other fields of information). In block 1, another transactions from user “i” to user “j”, and from user “j” to user “k” are also recorded. In block 2, several transactions may be recorded: a transaction from user “j” to user “n”, and a transaction to smart contract 16 a (indicated by “A_(γ)”) is recorded. Transaction Ay to smart contract 16 a may issue a unique digital article to user “p”, the unique digital article being defined by metadata 54 (here, correlated to a user-controllable character named “Dazzle Blanko”, having identifier “#010”, as depicted by a linked image of unique digital article 16, as well as including various other fields of information). In block 2, another transaction is recorded, from user “j” to user “n”. Based on the combination of unique digital articles owned by user “p”, a particular access request (to access particular media content) may be available to the user who controls the account of user “p”.

By way of non-limiting example, FIG. 5B illustrates a blockchain 117 d that includes several blocks (block 3, block 4, block 5), that have been appended to blockchain 117 c. Block 3 may be connected to block 2 (as indicated by link 50 c), block 4 may be connected to block 3 (as indicated by a link 50 d), and block 5 may be connected to block 4 (as indicated by a link 50 e). In block 3, another transaction may be recorded that modifies the ownership of the unique digital article (indicated by “Ax” and defined by metadata 52) to user “q”, such that user “p” no longer owns a “Camo Blanko”. Block 4 includes a transaction (indicated by a capital “T”) from user “i” to user “n”. For example, the transaction may represent a purchase of a first virtual item by user “n” from seller user “i”. Additionally, block 4 includes a transaction from user “p” to smart contract 15 a. For example, this transaction may represent user “p” requesting access to the particular media content, and this is no longer permitted since user “p” no longer owns a combination and/or collection including both a “Camo Blanko” and a “Dazzle Blanko”. Block 5 includes a transaction from user “n” to user “k”.

Referring to FIG. 1, in some implementations, online gaming platforms 105, server(s) 102, client computing platform(s) 104, administration servers 115, immutable ledger servers 111, media servers 119, and/or external resources 138 may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via one or more networks 13 such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which online gaming platforms 105, server(s) 102, client computing platform(s) 104, administration servers 115, immutable ledger servers 111, and/or external resources 138 may be operatively linked via some other communication media.

A given client computing platform 104 may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with the given client computing platform 104 to interface with system 100 and/or external resources 138, and/or provide other functionality attributed herein to client computing platform(s) 104. By way of non-limiting example, the given client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.

Administration server(s) 115 may include one or more of servers 102 a, processors 132 a, machine-readable instructions 106 a, electronic storage 130 a, and/or other components. Server(s) 102 a may be configured by machine-readable instructions 106 a. Machine-readable instructions 106 a may include one or more instruction components. The instruction components may include one or more of input component 135, communication component 137, and/or other instruction components. Administration server 115 may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. In some implementations, administration servers 115 may be used by one or more administrative users, e.g., to configure and/or control operation of system 100. In some implementations, administrative servers 115 may include or user one or more user interfaces to receive user input and/or otherwise interact with one or more administrative users.

External resources 138 may include sources of information outside of system 100, external entities participating with system 100, external providers of computation and/or storage services, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources 138 may be provided by resources included in system 100. In some implementations, external resources 138 may include one or more blockchain oracles (as may be used by monitoring component 118 to determine results for challenges).

Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. Illustration of server(s) 102 in FIG. 1 is not intended to be limiting. Server(s) 102 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s) 102. For example, server(s) 102 may be implemented by a cloud of computing platforms operating together as server(s) 102.

Electronic storage 130 may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage 130 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s) 102 and/or removable storage that is removably connectable to server(s) 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 130 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage 130 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 130 may store software algorithms, information determined by processor(s) 132, information received from server(s) 102, information received from client computing platform(s) 104, and/or other information that enables server(s) 102 to function as described herein.

Processor(s) 132 may be configured to provide information processing capabilities in server(s) 102. As such, processor(s) 132 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 132 is shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s) 132 may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s) 132 may represent processing functionality of a plurality of devices operating in coordination. Processor(s) 132 may be configured to execute components 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 131, 133, 134, 135, 136, 137, 139, 141, and/or 143, and/or other components. Processor(s) 132 may be configured to execute components 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 131, 133, 134, 135, 136, 137, 139, 141, and/or 143, and/or other components by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s) 132. As used herein, the term “component” may refer to any component or set of components that perform the functionality attributed to the component. This may include one or more physical processors during execution of processor readable instructions, the processor readable instructions, circuitry, hardware, storage media, or any other components.

It should be appreciated that although components 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 131, 133, 134, 135, 136, 137, 139, 141, and/or 143 are illustrated in FIG. 1 as being implemented within a single processing unit, in implementations in which processor(s) 132 includes multiple processing units, one or more of components 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 131, 133, 134, 135, 136, 137, 139, 141, and/or 143 may be implemented remotely from the other components. The description of the functionality provided by the different components 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 131, 133, 134, 135, 136, 137, 139, 141, and/or 143 described below is for illustrative purposes, and is not intended to be limiting, as any of components 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 131, 133, 134, 135, 136, 137, 139, 141, and/or 143 may provide more or less functionality than is described. For example, one or more of components 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 131, 133, 134, 135, 136, 137, 139, 141, and/or 143 may be eliminated, and some or all of its functionality may be provided by other ones of components 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 131, 133, 134, 135, 136, 137, 139, 141, and/or 143. As another example, processor(s) 132 may be configured to execute one or more additional components that may perform some or all of the functionality attributed below to one of components 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 131, 133, 134, 135, 136, 137, 139, 141, and/or 143.

FIG. 2 illustrates a method 200 to of providing gated media access based on collections of unique digital articles, in accordance with one or more implementations. The operations of method 200 presented below are intended to be illustrative. In some implementations, method 200 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 200 are illustrated in FIG. 2 and described below is not intended to be limiting.

In some implementations, method 200 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 200 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 200.

At an operation 202, an instance of a game is executed within an online gaming platform to facilitate presentation of the game to users, and in-game actions are implemented in the instance of the game in response to action requests for the in-game actions by the users. Presentation of the game is based on views of the game that are determined during execution of the instance of the game. The users include a first user and a second user. In some embodiments, operation 202 is performed by a game component the same as or similar to game component 108 (shown in FIG. 1 and described herein).

At an operation 204, user accounts are managed that are associated with the users. The user accounts include account inventories of virtual items. The user accounts include a first user account associated with the first user and a second user account associated with the second user. The first user account includes a first account inventory of a first set of virtual items. The second user account includes a second account inventory of a second set of virtual items. The first user controls the first set of virtual items in the first account inventory. The second user controls the second set of virtual items in the second account inventory. The first account inventory includes a first unique digital article configured to be used in the instance of the game. The second account inventory includes a second unique digital article configured to be used in the instance of the game. In some embodiments, operation 204 is performed by an account component the same as or similar to account component 112 (shown in FIG. 1 and described herein).

At an operation 206, a first set of instructions is received and executed to record the first ownership, by the first user, of the first unique digital article on the immutable ledger, and a second set of instructions is received and executed to record the second ownership, by the second user, of the second unique digital article on the immutable ledger. In some embodiments, operation 206 is performed by a transaction component and/or a receipt component the same as or similar to transaction component 134 and/or receipt component 136 (shown in FIG. 1 and described herein).

At an operation 208, a first access request is received, on behalf of the first user, to access particular media content. The access to the particular media content requires ownership of at least the first unique digital article and the second unique digital article. In some embodiments, operation 208 is performed by a request component the same as or similar to request component 139 (shown in FIG. 1 and described herein).

At an operation 210, it is determined whether the first user is recorded as owning both the first unique digital article and the second unique digital article. In some embodiments, operation 210 is performed by an ownership component the same as or similar to ownership component 141 (shown in FIG. 1 and described herein).

At an operation 212, responsive to determining the first user is not recorded as owning both the first unique digital article and the second unique digital article, the first action request is responded to by denying the first access request. In some embodiments, operation 212 is performed by an access component the same as or similar to access component 143 (shown in FIG. 1 and described herein).

At an operation 214, one or more instructions are received and executed to record the second ownership, by the first user, of the second unique digital article on the immutable ledger. In some embodiments, operation 214 is performed by a transaction component and/or a receipt component the same as or similar to transaction component 134 and/or receipt component 136 (shown in FIG. 1 and described herein).

At an operation 216, a second access request is received, on behalf of the first user, to access the particular media content. In some embodiments, operation 216 is performed by a request component the same as or similar to request component 139 (shown in FIG. 1 and described herein).

At an operation 218, it is determined whether the first user is recorded as owning both the first unique digital article and the second unique digital article. In some embodiments, operation 218 is performed by an ownership component the same as or similar to ownership component 141 (shown in FIG. 1 and described herein).

At an operation 220, responsive to determining the first user is recorded as owning both the first unique digital article and the second unique digital article, the second access request by accepting the second access request and granting access to the particular media content to the first user. In some embodiments, operation 220 is performed by an access component the same as or similar to access component 143 (shown in FIG. 1 and described herein).

Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. It is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with features of any other implementation. 

What is claimed is:
 1. A system configured to provide gated media access based on ownership of collections of unique digital articles, wherein the ownership of the unique digital articles is recorded on an immutable ledger that is an append-only ledger, the immutable ledger being implemented by a ledger server, wherein the system comprises: an online gaming platform including one or more hardware processors configured by machine-readable instructions to: execute, within the online gaming platform, an instance of a game to facilitate presentation of the game to users, and implement in-game actions in the instance of the game in response to action requests for the in-game actions by the users, wherein the presentation of the game is based on views of the game that are determined during execution of the instance of the game, wherein the users include a first user and a second user; and manage user accounts associated with the users, wherein the user accounts include account inventories of virtual items, wherein the user accounts include a first user account associated with the first user and a second user account associated with the second user, wherein the first user account includes a first account inventory of a first set of virtual items, wherein the second user account includes a second account inventory of a second set of virtual items, wherein the first user controls the first set of virtual items in the first account inventory, wherein the second user controls the second set of virtual items in the second account inventory, wherein the first account inventory includes a first unique digital article for which a first ownership by the first user has been recorded on the immutable ledger, and wherein the second account inventory includes a second unique digital article; and a media server that is separate from the online gaming platform, wherein the media server includes one or more particular processors configured by particular machine-readable instructions to: receive, on behalf of the first user, a first access request to access particular media content, wherein the access to the particular media content requires ownership of at least both of the first unique digital article and the second unique digital article; and responsive to determining the first user is not recorded as owning both the first unique digital article and the second unique digital article, respond to the first action request by denying the first access request; wherein the one or more hardware processors included in the online gaming platform are further configured to: effectuate recording a second ownership, by the first user, of the second unique digital article on the immutable ledger; wherein the one or more particular processors included in the media server are further configured to: receive, on behalf of the first user, a second access request to access the particular media content; and responsive to determining the first user is recorded as owning both the first unique digital article and the second unique digital article, respond to the second access request by accepting the second access request and granting access to the particular media content to the first user.
 2. The system of claim 1, wherein the access to the particular media content requires ownership of a particular collection of unique digital articles, wherein the unique digital articles in the particular collection includes at least a first type of unique digital articles and a second type of unique digital articles, wherein the first type of unique digital articles include the first unique digital article, and wherein the second type of unique digital articles include the second unique digital article.
 3. The system of claim 2, wherein the first type of unique digital articles include a set of unique digital articles are issued by a particular set of one or more smart contracts.
 4. The system of claim 3, wherein the second type of unique digital articles include a set of unique digital articles that were issued during a particular release.
 5. The system of claim 1, wherein the first unique digital article is associated with a first in-game user-controllable character that is configured to be controlled by the first user in the instance of the game.
 6. The system of claim 1, wherein the particular media content includes one or more of: (i) a previously-recorded video message, (ii) a live-streaming video channel, (iii) a text chat channel, (iv) a blog post, (v) previously-recorded audio content, and/or (vi) a live-streaming audio channel.
 7. The system of claim 1, wherein the one or more particular processors included in the media server are further configured to: receive a request for continued access to the particular media content; determine, at recurring intervals, whether the first user is still recorded as owning both the first unique digital article and the second unique digital article; responsive to determining the first user is still recorded as owning both the first unique digital article and the second unique digital article, respond to the request by continuing to grant access to the particular media content to the first user; and responsive to determining the first user is no longer recorded as owning both the first unique digital article and the second unique digital article, respond to the request by removing access to the particular media content to the first user.
 8. The system of claim 1, wherein the access to the particular media content requires ownership of at least the first unique digital article, the second unique digital article, and a third unique digital article.
 9. The system of claim 8, wherein the third type of unique digital article includes a set of unique digital articles that have received one or more participation rewards for (i) participating in an online event during a particular time-limited duration, or (ii) participating in a real-world event during the particular time-limited duration, or (iii) both (i) and (ii).
 10. The system of claim 1, further comprising the immutable ledger server configured to implement the immutable ledger.
 11. A method of providing gated media access based on ownership of collections of unique digital articles, wherein the ownership of the unique digital articles is recorded on an immutable ledger that is an append-only ledger, the immutable ledger being implemented by a ledger server, the method comprising: executing, within an online gaming platform, an instance of a game to facilitate presentation of the game to users, and implementing in-game actions in the instance of the game in response to action requests for the in-game actions by the users, wherein the presentation of the game is based on views of the game that are determined during execution of the instance of the game, wherein the users include a first user and a second user; managing user accounts associated with the users, wherein the user accounts include account inventories of virtual items, wherein the user accounts include a first user account associated with the first user and a second user account associated with the second user, wherein the first user account includes a first account inventory of a first set of virtual items, wherein the second user account includes a second account inventory of a second set of virtual items, wherein the first user controls the first set of virtual items in the first account inventory, wherein the second user controls the second set of virtual items in the second account inventory, wherein the first account inventory includes a first unique digital article for which a first ownership by the first user has been recorded on the immutable ledger, and wherein the second account inventory includes a second unique digital article; receiving, by a media server that is separate from the online gaming platform, on behalf of the first user, a first access request to access particular media content, wherein the access to the particular media content requires ownership of at least both of the first unique digital article and the second unique digital article; responsive to determining the first user is not recorded as owning both the first unique digital article and the second unique digital article, responding to the first action request by denying the first access request; effectuating a recordation of a second ownership, by the first user, of the second unique digital article on the immutable ledger; receiving, by the media server, on behalf of the first user, a second access request to access the particular media content; and responsive to determining the first user is recorded as owning both the first unique digital article and the second unique digital article, responding to the second access request by accepting the first access request and granting access to the particular media content to the first user.
 12. The method of claim 11, wherein the access to the particular media content requires ownership of a particular collection of unique digital articles, wherein the unique digital articles in the particular collection includes at least a first type of unique digital articles and a second type of unique digital articles, wherein the first type of unique digital articles include the first unique digital article, and wherein the second type of unique digital articles include the second unique digital article.
 13. The method of claim 12, wherein the first type of unique digital articles include a set of unique digital articles are issued by a particular set of one or more smart contracts.
 14. The method of claim 13, wherein the second type of unique digital articles include a set of unique digital articles that were issued during a particular release.
 15. The method of claim 11, wherein the first unique digital article is associated with a first in-game user-controllable character that is configured to be controlled by the first user in the instance of the game.
 16. The method of claim 11, wherein the particular media content includes one or more of: (i) a previously-recorded video message, (ii) a live-streaming video channel, (iii) a text chat channel, (iv) a blog post, (v) previously-recorded audio content, and/or (vi) a live-streaming audio channel.
 17. The method of claim 11, further comprising: receiving a request for continued access to the particular media content; determining, at recurring intervals, whether the first user is still recorded as owning both the first unique digital article and the second unique digital article; responsive to determining the first user is still recorded as owning both the first unique digital article and the second unique digital article, responding to the request by continuing to grant access to the particular media content to the first user; and responsive to determining the first user is no longer recorded as owning both the first unique digital article and the second unique digital article, responding to the request by removing access to the particular media content to the first user.
 18. The method of claim 11, wherein the access to the particular media content requires ownership of at least the first unique digital article, the second unique digital article, and a third unique digital article.
 19. The method of claim 18, wherein the third type of unique digital article includes a set of unique digital articles that have received one or more participation rewards for (i) participating in an online event during a particular time-limited duration, or (ii) participating in a real-world event during the particular time-limited duration, or (iii) both (i) and (ii).
 20. The method of claim 18, wherein the third type of unique digital article includes a set of unique digital articles that have received particular distribution gains by virtue of owning particular distribution rights. 